home *** CD-ROM | disk | FTP | other *** search
-
-
-
- RRRRTTTTMMMMOOOONNNN----DDDDUUUUMMMMPPPP((((1111)))) RRRRTTTTMMMMOOOONNNN----DDDDUUUUMMMMPPPP((((1111))))
-
-
-
- NNNNAAAAMMMMEEEE
- rtmon-dump - dump the contents of events collect from rtmond
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- rrrrttttmmmmoooonnnn----dddduuuummmmpppp [ _o_p_t_i_o_n_s ] [ file ]
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- rrrrttttmmmmoooonnnn----dddduuuummmmpppp prints binary event data collected from an rrrrttttmmmmoooonnnndddd(1) server
- process using rrrrttttmmmmoooonnnn----cccclllliiiieeeennnntttt(1) or ppppaaaaddddcccc(1). Data can be read from a file
- or from the standard input. By default, rrrrttttmmmmoooonnnn----dddduuuummmmpppp displays all
- interesting events found in a file using the same format as ppppaaaarrrr(1).
- Various options are provided for filtering which events are printed and
- how they are displayed.
-
- OOOOPPPPTTTTIIIIOOOONNNNSSSS
- ----dddd _u_s_e_c_s
- Use _u_s_e_c_s for the threshold for displaying system calls as begin and
- end entries. By default, rrrrttttmmmmoooonnnn----dddduuuummmmpppp will display system call events
- as single line if there are no events to display between the start
- and finish of the system call and if the duration of the system is
- less than a nominal threshold (default 2 milliseconds). If a system
- call takes longer than this threshold than it is displayed as
- separate begin and end events so that it is easy to pick out long-
- running calls.
-
- ----ffff Follow the growth of event data collected in a file. If a file is
- specified on the command line and the ----ffff option is specified, then
- rrrrttttmmmmoooonnnn----dddduuuummmmpppp will dump the contents of the file and then periodically
- monitor it for new data. In this situation rrrrttttmmmmoooonnnn----dddduuuummmmpppp will never
- exit voluntarily; it must be terminated with an interrupt signal
- (e.g. from a keyboard interrupt).
-
- ----iiii Display ``internal'' event as well as normal events. This option
- causes the display of certain events that are normally used only in
- decoding other events: CPU configuration, task names, process
- execs, etc.
-
- ----mmmm _e_v_e_n_t-_m_a_s_k
- Display only events specified by _e_v_e_n_t-_m_a_s_k. An _e_v_e_n_t _m_a_s_k
- specifies a set of events; it is a set of _e_v_e_n_t _c_l_a_s_s_e_s with each
- class specified symbolically as one of the following:
-
- NNNNaaaammmmeeee DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn
- all All events (default)
- alloc Memory allocation
- disk Disk i/o work
- intr Hardware interrupts
- io I/O-related events (disk+intr)
- netflow Network I/O flow
- netsched Network I/O scheduling
- network Network-related events (netflow+netsched)
- none No events
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- RRRRTTTTMMMMOOOONNNN----DDDDUUUUMMMMPPPP((((1111)))) RRRRTTTTMMMMOOOONNNN----DDDDUUUUMMMMPPPP((((1111))))
-
-
-
- profile Kernel profiling
- scheduler Process and thread scheduler
- signal Signal delivery and reception
- syscall System calls and their arguments
- task Process and thread scheduling
- taskproc Process scheduling (system threads are not included)
- vm Virtual memory operation
-
- Event class names are case insensitive; i.e. ``SIGNAL'' is
- interpreted the same as ``signal''. Multiple event classes may be
- included by using a ``+'', ``|'', or ``,'' symbol to separate the
- names. Event classes may be excluded by using a ``-'' to separate
- the name. For example, ``network+io-disk'' indicates all network
- and i/o events should be included except for disk-related events.
- In addition to the above names, a number may be used to specify a
- value, where the various events are selected by bits in the value,
- as defined in ``<sys/rtmon.h>''.
-
- ----OOOO Print unrecognized event data in octal instead of decimal.
-
- ----xxxx Print unrecognized event data in hexadecimal instead of decimal.
-
- ----pppp _c_p_u-_l_i_s_t
- Display only events from certain CPUs. CPUs are specified as a
- comma-separated list of CPU numbers or range of CPU numbers. CPUs
- are numbered starting at zero. For example, ----pppp _1,_4-_7,_1_1 means
- processors 1, 4, 5, 6, 7, and 11. An open-ended range is
- interpreted as all CPUs to the maximum CPU number; e.g. _2- on an
- 8-processor system is the same as _2-_7. The CPU list must be one
- string with no white space. By default, rrrrttttmmmmoooonnnn----dddduuuummmmpppp displays events
- from all CPUs.
-
- ----rrrr Display event decoding; display all events as raw data.
-
- ----uuuu Display event times as milliseconds with a microsecond fraction and
- show the number of microseconds between displayed events.
-
- ----vvvv Enable verbose output.
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- ppppaaaaddddcccc(1), ppppaaaarrrr(1), rrrrttttmmmmoooonnnndddd(1), rrrrttttmmmmoooonnnn____lllloooogggg____uuuusssseeeerrrr____ttttssssttttaaaammmmpppp(3)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-